Revised 07/02/89

The key word here is 'guidelines', these are not rules or laws,
since the GT Network has no formal organization I am just letting
everyone know the basic guidelines for requesting and maintaining
echo sponsorship.


A)  The requesting Sysop MUST possess a valid Net/Node in the GT
    Network as reflected in the current NODELIST.

B)  The subject of the conference requested MUST not already exist (or
    be substantially the same) as a current conference.

C)  The subject of the conference MUST not threaten the general
    reputation of the GT Network.

D)  The requesting Sysop MUST furnish the time (Central) that the echo
    will be available for pickup, etc.  This information MUST be
    furnished on the 'official form' included in the SPONSORS.KIT, all
    requests which are not on the form will be rejected.

E)  The requesting Sysop if not PCPable SHOULD try to establish a link
    with a node that is on the PCP network for the purpose of pickup
    and distribution of the conference since PCP is the primary out of
    net distribution method at the present time.  STARLINK may be
    added to MDriver in the future to help cut phone costs and could
    also be utilized in helping to distribute echo conferences.

F)  The requesting Sysop SHOULD provide data for the ECHOmmdd.LVL and
    ECHOmmdd.SRC reports at least once a month, and to provide that
    information to the Net/Node specified by the IEC.  The data is
    currently sent to 001/000.  The reports are used to create two
    listings, a level report and a source report, which can be used to
    locate a pickup point by those who wish to subscribe.  Any echo
    sponsor who has not sent in his echo chain report will simply be
    shown with no data as to who is carrying the conference(s).

G)  The requesting Sysop MUST immediately abandon the use of any issued
    CRC and stop attempting to distribute an Echomail conference that
    is **RETIRED** from the ECHOMAIL.BBS listing.

H)  The requesting Sysop SHOULD make an effort to remove duplicate
    messages from his conference.  This can be done manually as the
    conference is read, or there are several programs which will delete
    duplicate messages from your message areas.  This should be done
    before the daily bagging of your new messages into E bags.

I)  This is the last guideline, anything not covered in A thru H is
    covered by this last guideline, COMMON SENSE.

Cam DeBuck
IEC Caretaker